Search Results fnd_product_installations

Overview

The FND_PRODUCT_INSTALLATIONS table is a core Applications DBA (AD) table within the APPLSYS schema that serves as the system of record for tracking which Oracle E-Business Suite products and modules are installed at a given site. It is a fundamental component of the application's architecture, enabling the system to manage product-specific features, dependencies, and configurations. Its primary role is to maintain the inventory of installed applications, linking each product to its designated ORACLE_ID (database schema). This relationship is critical for operations that require context about the owning schema for a particular application, such as patch management, module initialization, and dependency validation.

Key Information Stored

The table's structure centers on two primary foreign key columns that form its composite primary key. The APPLICATION_ID column references FND_APPLICATION.APPLICATION_ID, uniquely identifying an E-Business Suite product like General Ledger (SQLGL) or Payables (SQLAP). The ORACLE_ID column references FND_ORACLE_USERID.ORACLE_ID, which maps to the specific database schema (e.g., GL, AP) that owns the database objects for that product. Together, these columns create a definitive list of valid application-to-schema mappings for the installation. While the provided metadata highlights these core columns, the table typically includes additional status columns (like STATUS or PATCH_LEVEL) to indicate the installation state of each product.

Common Use Cases and Queries

This table is frequently queried for installation audits, troubleshooting, and during upgrade or patching activities. A common use case is generating a simple report of all installed products with their corresponding database schemas. Another critical use is validating the installation environment before applying patches or performing upgrades. Database administrators and functional consultants often reference this table to confirm that prerequisite products are installed and active. For example, a typical query to list installed applications would be:

• SELECT fpi.application_id, fa.application_short_name, fa.application_name, fou.oracle_username FROM apps.fnd_product_installations fpi, apps.fnd_application fa, apps.fnd_oracle_userid fou WHERE fpi.application_id = fa.application_id AND fpi.oracle_id = fou.oracle_id ORDER BY fa.application_short_name;

Related Objects

As indicated by the foreign key relationships, FND_PRODUCT_INSTALLATIONS is centrally linked to several key metadata tables. It has foreign key dependencies on FND_APPLICATION (for the product definition) and FND_ORACLE_USERID (for the schema definition). Furthermore, it is referenced by other important configuration tables. The table ALR_ACTION_SET_CHECKS references it to define product-specific alert checking. Most significantly, the FND_PRODUCT_DEPENDENCIES table references it twice: once to define the dependent product (APPLICATION_ID, ORACLE_ID) and again to define the product that is required (REQUIRED_APPLICATION_ID, REQUIRED_ORACLE_ID). This makes FND_PRODUCT_INSTALLATIONS essential for the system's dependency resolution engine.