Results for “required_application_id”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

FND_PRODUCT_DEPENDENCIES is a core Applications DBA (AD) dictionary table owned by the APPLSYS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. The table records the inter-product dependency graph for every Oracle Applications product registered at a site, capturing which installed products require other installed products in order to function correctly. Each row associates a dependent product (the requestor) with a product it depends upon (the requisite), keyed by both the numeric APPLICATION_ID and the short ORACLE_ID product code.

Under a heuristic Data Vault classification derived from its foreign-key structure, this table models as a link entity. It contains no descriptive attributes of its own beyond audit columns; instead it resolves a many-to-many relationship between product installations and the products they require. Both FK pairs point back to FND_PRODUCT_INSTALLATIONS, confirming the link interpretation between two instances of the same hub.

Key Information Stored

The documented physical schema contains nine columns. The four structural columns form the composite primary key:

• APPLICATION_ID — the numeric identifier of the dependent (installed) product, from FND_APPLICATION.
• ORACLE_ID — the short product code (for example, "SQLAP" or "GL") of the dependent product.
• REQUIRED_APPLICATION_ID — the numeric identifier of the product that must be installed for the dependent product to operate.
• REQUIRED_ORACLE_ID — the short product code of the required product.

The unique index FND_PRODUCT_DEPENDENCIES_U1 is defined over all four of these columns, making them the business-key candidate that guarantees a single dependency record per product pair. There is no separate surrogate key; the dependency itself is the identity.

The remaining five columns are standard AD audit attributes: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN. These record who inserted or last modified a dependency row and when, which is useful when auditing patching or installation activity.

Common Use Cases and Queries

The most frequent use is resolving "what does product X need?" or the inverse "what depends on product Y?" before applying a patch, running an upgrade, or sequencing an implementation. The following query lists the products required by a given dependent product:

• SELECT REQUIRED_APPLICATION_ID, REQUIRED_ORACLE_ID FROM FND_PRODUCT_DEPENDENCIES WHERE APPLICATION_ID = :app_id;
• SELECT APPLICATION_ID, ORACLE_ID FROM FND_PRODUCT_DEPENDENCIES WHERE REQUIRED_APPLICATION_ID = :req_app_id; — reverse lookup of dependents.

Join to FND_PRODUCT_INSTALLATIONS (or FND_APPLICATION) to translate IDs into readable product names for reporting, dependency matrices, and impact analysis. The table also supports validation of install order: a product cannot be applied before its required products are already installed. Because the ORACLE_ID columns duplicate the numeric identifiers, queries may filter on either form, though the numeric keys are preferred for joins.

Related Objects

FND_PRODUCT_DEPENDENCIES is closely coupled to the product registration framework:

• FND_PRODUCT_INSTALLATIONS — referenced twice: on (APPLICATION_ID, ORACLE_ID) and on (REQUIRED_APPLICATION_ID, REQUIRED_ORACLE_ID). This is the primary parent for both FK relationships.
• FND_APPLICATION — resolves APPLICATION_ID and REQUIRED_APPLICATION_ID to product names and base paths.
• FND_PRODUCT_GROUPS — groups related products and is often queried alongside dependencies when planning installations.
• AD_PATCH_DRIVER_DATA and related AD patch tables — patch prerequisites frequently align with the dependencies recorded here.
• FND_ORACLE_USERID — identifies the Oracle schema owned by each product, useful when validating that a required product's schema exists.

Because both foreign keys target the same parent, any join to FND_PRODUCT_INSTALLATIONS must alias that table twice — once for the dependent product and once for the required product — to avoid ambiguous column references.