Search Results fnd_product_dependencies




Overview
Explore in AI Chat

Overview

The FND_PRODUCT_DEPENDENCIES table is a core repository table within the Oracle E-Business Suite (EBS) Applications DBA (AD) product family. It serves as the system of record for defining and enforcing prerequisite relationships between installed Oracle Applications products. Its primary role is to maintain the dependency map, ensuring that for any given product, all required supporting products are correctly installed and configured. This metadata is critical for system integrity, guiding installation, upgrade, and patching processes by preventing operations that would violate established dependencies. The table is owned by the APPLSYS schema and is a foundational component of the EBS architecture in both releases 12.1.1 and 12.2.2.

Key Information Stored

The table's structure centers on defining a relationship between a dependent product and a product it requires. The primary key is a composite of four columns, ensuring a unique dependency rule. The key columns are APPLICATION_ID and ORACLE_ID, which together identify the product that has the dependency. The columns REQUIRED_APPLICATION_ID and REQUIRED_ORACLE_ID identify the prerequisite product that must be present. These ID pairs link directly to the FND_PRODUCT_INSTALLATIONS table, which holds the master list of products registered at the site. The table does not store version-level dependencies but establishes product-level prerequisites.

Common Use Cases and Queries

This table is primarily queried by installation and upgrade utilities, such as AutoInstall (AD), to validate the environment before applying changes. Database administrators and functional consultants use it for impact analysis. A common reporting need is to list all dependencies for a specific product. For example, to find all products required by Oracle General Ledger (APPLICATION_ID=101), one would execute:

  • SELECT required_application_id, required_oracle_id FROM apps.fnd_product_dependencies WHERE application_id = 101;

Conversely, to identify all products that depend on a given product, a reverse lookup is used:

  • SELECT application_id, oracle_id FROM apps.fnd_product_dependencies WHERE required_application_id = &TARGET_APP_ID;

These queries are essential for assessing the downstream impact of disabling or removing a product module.

Related Objects

FND_PRODUCT_DEPENDENCIES has defined foreign key relationships with the FND_PRODUCT_INSTALLATIONS table, which is the central source for product registration. Two foreign keys exist:

  • From columns (APPLICATION_ID, ORACLE_ID) to FND_PRODUCT_INSTALLATIONS. This links the dependent product to its master record.
  • From columns (REQUIRED_APPLICATION_ID, REQUIRED_ORACLE_ID) to FND_PRODUCT_INSTALLATIONS. This links the prerequisite product to its master record.

This structure ensures referential integrity, meaning a dependency can only be defined for products that are officially registered in the FND_PRODUCT_INSTALLATIONS table. The table is also referenced by various internal AD utilities and may be joined with FND_APPLICATION_VL and FND_ORACLE_USERID_VL views to translate IDs into human-readable names for reports.