Search Results clean_tables

Overview

FND_IMP_DEPENDENCY_PKG is an Oracle E-Business Suite (EBS) PL/SQL package owned by the APPS schema and classified under the "OTHER" API category. It forms part of the dependency-tracking infrastructure used by the Oracle EBS patching and file-delivery framework, particularly in conjunction with snapshot and dependency metadata used by AutoPatch and related utilities. The package manages the registration of the individual file objects that make up an application snapshot and the parent-child dependency relationships that exist between those objects. This enables Oracle Applications Manager and the patching engine to understand which files depend on which others, so that snapshots can be compared and merged intelligently.

The package is declared AUTHID CURRENT_USER, meaning that procedures execute with the privileges of the calling database user rather than the definer, and it follows the standard FND API convention by accepting an API version, an initialization flag, and a commit flag, and returning standard return status and message outputs. The header ($Header: afimpdeps.pls 120.4 2010/07/12) confirms that it is a long-standing shipped file in Release 12.1.1 and 12.2.2.

Key Procedures and Functions

The ETRM metadata documents three procedures in this package:

• INSERT_DEP_OBJECT — Registers a single object (typically a file) belonging to an application snapshot. It accepts a wide set of descriptive attributes such as object name, object type, application short name, file directory, filename, file type, RCS identifier, checksums, and ten generic attribute slots. It returns the generated object identifier and object version number to the caller, along with the standard return status, message count, and message data.
• INSERT_DEP_RELATION — Creates a dependency relationship between a parent object and a child object, both identified by object ID and associated with a snapshot. It also accepts a dependency type indicator and returns the standard API outputs.
• CLEAN_TABLES — Removes or purges stale staging data from the dependency tables. This procedure is the one most commonly referenced by administrators and by error messages that mention "clean_tables" when a snapshot load fails or leaves orphaned rows. It is normally used to reset the working tables between snapshot operations.

Tables Accessed

The package reads and writes the following documented tables:

• FND_IMP_DEPOBJECTS — The base table storing object-level dependency records created by INSERT_DEP_OBJECT.
• FND_IMP_DEPOBJECTS_S — The translated (or shadow) table paired with FND_IMP_DEPOBJECTS, maintained alongside the base table.
• FND_IMP_DEPRELATIONS — Stores parent-child dependency relationships generated by INSERT_DEP_RELATION.
• AD_SNAPSHOTS — The snapshot header table; the package references it to validate or associate objects and relations with an existing snapshot.
• DUAL — Used internally for simple PL/SQL expressions and validation queries.

Usage Notes

FND_IMP_DEPENDENCY_PKG is not documented as being referenced by any other package, which indicates that it is called directly by the patching utilities or by the AutoPatch/AD utilities rather than as an internal subroutine of another PL/SQL API. It is typically invoked during snapshot creation and dependency-analysis operations — for example, when AD utilities build an inventory of files and their inter-dependencies for a patch or an ADOP online patching cycle.

Because it is an APPS-owned package with no documented form or concurrent program wiring in the ETRM excerpt, custom code and diagnostic scripts may call it directly. The combination of p_init_msg_list and p_commit flags allows callers to control transaction boundaries explicitly, which is important when bulk-loading snapshot data. The CLEAN_TABLES procedure is the documented entry point for clearing residual rows; administrators troubleshooting failed snapshot operations should invoke it before re-running the load to avoid duplicate or orphaned dependency records.