Search Results fnd_module_installations




Overview
Explore in AI Chat

Overview

The FND_MODULE_INSTALLATIONS table is a core Applications DBA (AD) repository within the Oracle E-Business Suite (EBS) APPLSYS schema. It serves as the system of record for tracking which specific Oracle Application modules are installed and configured at a given site. This table is fundamental to the architecture of EBS 12.1.1 and 12.2.2, as it provides a definitive mapping between installed software modules, their parent applications, and the associated Oracle database schemas (users) that own their underlying database objects. The data in this table is critical for system administration, patching, and upgrade processes, ensuring that operations target only the relevant modules for a particular installation.

Key Information Stored

The table's structure centers on a composite primary key that uniquely identifies an installed module instance. The key columns are APPLICATION_ID, which links to the FND_APPLICATION table to identify the product family; ORACLE_ID, which links to the FND_ORACLE_USERID table to identify the database schema (e.g., GL, AP, PO) that owns the module's objects; and MODULE_SHORT_NAME, which is the abbreviated identifier for the specific module itself. Together, these columns create a precise record of a module's installation context. While the provided metadata does not list all columns, the primary and foreign key relationships confirm that this table is the central junction between the application product, the module, and its physical database implementation.

Common Use Cases and Queries

This table is primarily queried for inventory and validation purposes. A common use case is generating a report of all installed modules for a specific product family or database schema, which is essential during pre-upgrade assessments or audits. Database administrators and functional consultants use this data to verify module installation status before applying patches or enabling new functionality. A typical query pattern involves joining with its referenced tables to retrieve meaningful names.

  • Sample Query to List Installed Modules:
    SELECT fa.APPLICATION_SHORT_NAME, fou.ORACLE_USERNAME, fmi.MODULE_SHORT_NAME
    FROM APPLSYS.FND_MODULE_INSTALLATIONS fmi,
         APPLSYS.FND_APPLICATION fa,
         APPLSYS.FND_ORACLE_USERID fou
    WHERE fmi.APPLICATION_ID = fa.APPLICATION_ID
    AND fmi.ORACLE_ID = fou.ORACLE_ID
    ORDER BY 1, 2, 3;
  • Verifying a Specific Module: Queries often filter on MODULE_SHORT_NAME (e.g., 'PAYROLL') in conjunction with an APPLICATION_ID or ORACLE_USERNAME to confirm its installation in a specific context.

Related Objects

The FND_MODULE_INSTALLATIONS table has defined dependencies on two key foundation tables in the APPLSYS schema, as per the provided relationship data.

  • FND_APPLICATION: Linked via the foreign key on the APPLICATION_ID column. This table defines all registered applications (product families) in the EBS system.
  • FND_ORACLE_USERID: Linked via the foreign key on the ORACLE_ID column. This table maintains a list of all Oracle database schemas (users) associated with the EBS installation, such as GL, AR, and INV.

The table itself, with its primary key FND_MODULE_INSTALLATIONS_PK, is a referenced object for various internal processes and potentially for other metadata tables that depend on the definitive list of installed modules.