Search Results fnd_application




The FND_APPLICATION table is a fundamental data dictionary table within Oracle E-Business Suite (EBS) Release 12.1.1 and 12.2.2, serving as a core repository for application metadata. It stores critical information about registered applications, modules, and products that constitute the Oracle EBS ecosystem. This table is part of the Oracle Application Object Library (FND), which provides the foundational framework for EBS functionality, including security, navigation, and application integration.

Structure and Key Columns

The FND_APPLICATION table consists of several key columns that define and manage application properties:
  • APPLICATION_ID: A unique numeric identifier for each application, often used as a foreign key in other EBS tables.
  • APPLICATION_SHORT_NAME: A concise, uppercase code representing the application (e.g., 'GL' for General Ledger, 'AP' for Accounts Payable).
  • APPLICATION_NAME: The full descriptive name of the application (e.g., 'General Ledger', 'Payables').
  • PRODUCT_CODE: A legacy column indicating the product family affiliation.
  • BASEPATH: Specifies the base directory path for the application's files.
  • DESCRIPTION: A detailed description of the application's purpose.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY: Audit columns tracking record changes.

Functional Role in Oracle EBS

The FND_APPLICATION table plays a pivotal role in:
  1. Application Registration: All EBS modules must be registered here before integration with the suite.
  2. Security Framework: Forms the basis for function and menu security through relationships with FND_FORM_FUNCTIONS and FND_MENUS.
  3. Navigation: Enables the EBS Navigator to display available modules based on user responsibilities.
  4. Dependency Management: Tracks application relationships for patch and upgrade processes.

Integration with Other Key Tables

The table maintains relationships with several critical EBS tables:
  • FND_APPLICATION_TL: Stores translated application names for multilingual implementations.
  • FND_RESPONSIBILITY: Links applications to security responsibilities.
  • FND_FORM_FUNCTIONS: Associates applications with their executable functions.
  • AD_PATCHABLE_APPS: Used by patching utilities to identify patchable applications.

Technical Considerations

For EBS 12.1.1 and 12.2.2 implementations:
  • The table is typically populated during installation via AutoConfig.
  • Direct DML operations are discouraged; modifications should use Oracle Application Developer (OAD) utilities.
  • In 12.2.2, the table remains structurally consistent with 12.1.1 but may contain additional registered applications.
  • Custom applications require proper registration in this table for full EBS integration.

Common Use Cases

Administrators and developers frequently query FND_APPLICATION for:
  • Troubleshooting module visibility issues
  • Auditing installed applications
  • Developing custom reports on application usage
  • Validating application dependencies before patches
The FND_APPLICATION table's central role in Oracle EBS architecture makes it essential for system administrators, implementers, and developers to understand its structure and relationships when customizing, maintaining, or troubleshooting the EBS environment.