Search Results fnd_imp_deprelations




Overview
Explore in AI Chat

Overview

FND_IMP_DEPRELATIONS is a repository table in the Oracle E-Business Suite APPLSYS schema, part of the FND (Application Object Library) product family. It stores dependency relationships between imported metadata objects, recording how one object (the parent) depends on another (the child) within a given snapshot. This information is consumed by Oracle EBS patching and metadata import utilities to determine the correct sequencing of object creation, validation, and compilation during patch application, ADOP-based online patching in 12.2.2, and snapshot manipulation. Each row captures a directed dependency from a parent object to a child object, along with the type of dependency and its position within the dependency graph.

The heuristic Data Vault classification mined from the documented foreign key structure is standalone. From a dimensional modeling perspective, this suggests the table functions more as a self-contained dependency map than as a classic hub, link, or satellite. It carries its own business key and references external entities (AHL_SNAPSHOTS, FND_SECURITY_GROUPS) via foreign keys rather than acting as a pure junction between two conformed hubs.

Key Information Stored

The table contains 18 documented columns in the ETRM 12.2.2 schema. The most significant include:

The business-key candidate is defined by the unique index FND_IMP_DEPRELATIONS_U1 on the combination (SNAPSHOT_ID, PARENT_OBJECT_ID, CHILD_OBJECT_ID, DEPENDENCY_TYPE). The metadata does not document a separate single-column surrogate primary key.

Common Use Cases and Queries

This table is primarily queried during patch analysis and metadata diagnostics. Typical scenarios include identifying all children that a given parent depends on within a snapshot, and detecting potential circular dependencies before patch application.

Example — list dependencies for a specific snapshot and parent object:

SELECT parent_object_name, child_object_name,
       dependency_type, graph_dependency
FROM   applsys.fnd_imp_deprelations
WHERE  snapshot_id = :snapshot_id
AND    parent_object_id = :parent_object_id;

Example — find all objects depending on a specific child:

SELECT parent_object_name, parent_app_short_name, dependency_type
FROM   applsys.fnd_imp_deprelations
WHERE  child_object_name = 'FND_OBJECTS'
AND    snapshot_id = :snapshot_id;

Reporting use cases include dependency graph visualization, patch impact assessment, and reconciliation of imported object hierarchies between source and target environments.

Related Objects

  • AHL_SNAPSHOTS — joined on SNAPSHOT_ID = AHL_SNAPSHOTS.SNAPSHOT_ID; scopes each dependency to its snapshot.
  • FND_SECURITY_GROUPS — joined on SECURITY_GROUP_ID = FND_SECURITY_GROUPS.SECURITY_GROUP_ID; enforces group-level security.
  • FND_OBJECTS — a logical companion holding object metadata referenced by the object name and ID columns.
  • FND_OBJECT_INSTANCES — related object-instance registry used during import processing.
  • AD_APPLIED_PATCHES — consumed by patching utilities that interpret dependency ordering.

Queries against this table should generally be filtered by SNAPSHOT_ID to avoid scanning across all stored snapshots and to respect security-group scoping.