Search Results insert_dep_object




Overview
Explore in AI Chat

Overview

APPS.FND_IMP_DEPENDENCY_PKG is an Oracle E-Business Suite PL/SQL package body that manages the metadata describing dependency objects and dependency relationships used during an Application Dependencies (AD) snapshot cycle. The package header carries the version string afimpdepb.pls 120.2 2005/11/02, identifying it as part of the FND import dependency infrastructure shipped with Oracle EBS. It exposes an API-classified interface (API classification: OTHER in the 12.2.2 ETRM registry) that allows callers to persist individual dependency objects, persist relationships between those objects, and purge stale or obsolete rows from the working tables. It is a low-level data-maintenance package rather than an end-user-facing business API; it is consumed internally by the AD snapshot and dependency-tracking components. The package initializes two global variables at load time, G_LOGIN_ID and G_USER_ID, sourced from FND_GLOBAL.CONC_LOGIN_ID and FND_GLOBAL.USER_ID, so that auditable inserts carry the concurrent login context.

Key Procedures and Functions

The 12.2.2 ETRM registry documents three procedures for this package body.

  • INSERT_DEP_OBJECT — Inserts a single dependency object record into FND_IMP_DEPOBJECTS. The documented signature follows the standard Oracle EBS API convention: an p_api_version input, p_init_msg_list, and p_commit control parameters; an OUT NOCOPY surrogate key p_object_id; and descriptive inputs covering p_snapshot_id, p_object_name, p_object_type, p_app_short_name, file-location attributes (p_file_directory, p_filename, p_file_type), version-control attributes (p_rcs_id, p_ochksum, p_fchksum), and ten generic p_attrib0 through p_attrib9 slots. It returns p_object_version_number and the standard x_return_status, x_msg_count, and x_msg_data outputs. A local sequence_cursor is declared to obtain the next object identifier.
  • INSERT_DEP_RELATION — Persists a parent/child or otherwise directed relationship between dependency objects in FND_IMP_DEPRELATIONS, tying two object rows to the snapshot to which they belong.
  • CLEAN_TABLES — Removes obsolete or orphaned rows from the dependency working tables, typically invoked after a snapshot is promoted or abandoned so that stale object and relation data does not accumulate.

Tables Accessed

The package reads and writes the following objects through APPS synonyms:

  • FND_IMP_DEPOBJECTS — the primary staging table for dependency object definitions; the target of INSERT_DEP_OBJECT and the source for version-number and checksum lookups.
  • FND_IMP_DEPRELATIONS — stores the directed links between objects created by INSERT_DEP_RELATION.
  • FND_IMP_DEPOBJECTS_S — the shadow/intersection table that records the objects belonging to each snapshot; referenced during object identification and clean-up.
  • AD_SNAPSHOTS — the AD snapshot registry, used to validate the snapshot identifier passed to INSERT_DEP_OBJECT.
  • DUAL — used for sequence and single-row scalar evaluation.

Usage Notes

FND_IMP_DEPENDENCY_PKG is invoked programmatically rather than from a standard Oracle Forms UI. ETRM records zero other packages referencing it, which indicates it sits at the bottom of the call stack and is called by AD snapshot/dependency concurrent programs or by custom PL/SQL that must register objects and relations before generating or applying a snapshot. Callers should populate the standard API arguments: pass FND_API.G_FALSE for p_init_msg_list when the caller has already reset the message stack, and pass FND_API.G_TRUE for p_commit only when the transaction boundary should be closed by the API. Because the ten attrib columns are generic, their meaning is defined by the caller, so custom integrations must document their own conventions. The package is compatible with both 12.1.1 and 12.2.2; in 12.2.x environments it remains part of the APPS schema and is subject to the same online patching restrictions as other AD snapshot components.